Swagger specifications for 2019-10-01 Tags API for resources and subscriptions#7716
Conversation
Automation for azure-sdk-for-pythonA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-goNothing to generate for azure-sdk-for-go |
|
Can one of the admins verify this patch? |
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Outdated
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Outdated
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Outdated
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Outdated
Show resolved
Hide resolved
|
How about "Swagger specifications for 2019-10-01 Tags API for resources and subscriptions" |
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Outdated
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Outdated
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Outdated
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Outdated
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Outdated
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Outdated
Show resolved
Hide resolved
| "type": "object", | ||
| "description": "Tag Request for Patch operation.", | ||
| "properties": { | ||
| "operation": { |
There was a problem hiding this comment.
this I think should be generalized. We should create an Azure extension (similar to x-ms-long-running). and then any service who want to support advanced patch capabilities can leverage that extension. something like - "x-ms-patch-mode"
@anthony-c-martin @KrisBash - thoughts?
There was a problem hiding this comment.
Since the request body for put and patch is different here, we have defined two entities: TagPatchRequest and TagRequest.
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Outdated
Show resolved
Hide resolved
specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json
Outdated
Show resolved
Hide resolved
|
@ChenTanyi Hello, Tianyi, Arm Team has approved this pull request, could we merge this PR? Thanks. |
|
@Grayer123 sorry, I haven't seen the arm sign off label. I can't merge it. If the arm team approved, they would change the label to arm sign off |
|
@ChenTanyi Thanks. Please merge the PR |
…criptions (Azure#7716) * Added previous version spec as initial commit. * Modified all the api-version for the existing example files. * Added tag related api spec to resource file as well add example files. * Modified readme related files. * Execute prettier to reorganize the file. * Pull request comments related fixes. * Use scope to support nested resources for tags. * Update examples based on scope change. * Remove first slash to resolve model validation error. * Combine tracked resource and subscription apis for tags. * Modifed the examples to match the changes in resource.json. * Utilize the shared parameters, and update the examples. * Removing "required" from TagPatchRequest as getting R2016 error. * Collapse TagRequest and TagResponse into TagsResource. * Removed 404 response as covered in default scenario, as well updated corresponding examples.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Detailed Changes:
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.